We're working on upgrading from DOORS 8.1 to 8.3, and want to use Terminal Services for the 8.3 client (currently, the 8.1 client is installed on individual desktops, but they have recently locked out admin rights on desktops, so it's a major hassle to get the client installed now).
What's the best way to handle project and menu addins, such as WEXP, in a Terminal Services implementation? As the DOORS DBM, I would prefer to be allowed to add/modify menu addins as the need arises, but my server admin says there are issues that will prevent me from directly accessing the Terminal Services DOORS client (don't know the specifics, but can get more detail on this if needed).
If we maintained the addins in a secured folder on the network, can we direct the client to use the network location containing the addin items? How would we accomplish this?
Thanks for any input,
Karrin
karringordon - Thu Mar 26 10:48:20 EDT 2009 |
|
Re: How to manage dxl/addins with Terminal Services DOORS client
llandale - Thu Mar 26 12:14:32 EDT 2009
If you structure your DXL on the network in suitable format, in suitable folder hierarchies with suitable sibling *.idx and *.hlp files, you can tell DOORS to build menus of those DXL by modifying the 'addins' and 'projectaddins' Registry values for DOORS. You can also create your own doors.exe shortcut and add command line switches that will accomplish the same thing. Both those methods may not be available to you, but the admins may be willing to create the icon for you and let you run it.
Look for section 'The DXL Library and Addins menus' in the DXL manual, to get you started on the long road of massive confusion.
>Louie
|
|
Re: How to manage dxl/addins with Terminal Services DOORS client
karringordon - Thu Mar 26 15:09:55 EDT 2009
Thanks Louie. I've read the chapter you reference, and agree, very confusing. I'm not a big DXL writer, just kind of fumble along, so it doesn't take much to confuse me :-/ I've searched my registry and don't find any keys labeled "addins" or "projectaddins". A reg key called "addins" defined with the value of the network path/folder containing the appropriate file structure and contents for the addin menu items seems like a perfectly reasonable approach to me, but I can't find such keys, and wouldn't know where to create them so that DOORS would know to reference them. Am I way off base? Do you have such registry keys, and if so, where in the Telelogic registry tree are they located?
|
|
Re: How to manage dxl/addins with Terminal Services DOORS client
SystemAdmin - Fri Mar 27 10:07:37 EDT 2009 karringordon - Thu Mar 26 15:09:55 EDT 2009
Thanks Louie. I've read the chapter you reference, and agree, very confusing. I'm not a big DXL writer, just kind of fumble along, so it doesn't take much to confuse me :-/ I've searched my registry and don't find any keys labeled "addins" or "projectaddins". A reg key called "addins" defined with the value of the network path/folder containing the appropriate file structure and contents for the addin menu items seems like a perfectly reasonable approach to me, but I can't find such keys, and wouldn't know where to create them so that DOORS would know to reference them. Am I way off base? Do you have such registry keys, and if so, where in the Telelogic registry tree are they located?
An alternative method is to use the -addins switch for the DOORS icon properties, e.g. -addins "\\server\dxlshare".
|
|
Re: How to manage dxl/addins with Terminal Services DOORS client
karringordon - Fri Mar 27 10:45:45 EDT 2009
I just finished testing both approaches, the reg key and the shortcut command line switch. Both work great, couldn't have been easier. Am now awaiting my server admin to decide which approach we'll use in our Terminal Services implementation.
Thanks for your help and speedy replies,
Karrin
|
|
Re: How to manage dxl/addins on several client installations
muthurani - Fri Sep 10 06:06:49 EDT 2010 SystemAdmin - Fri Mar 27 10:07:37 EDT 2009
You can add the addins value yourself to the Config section of DOORS Client key in registry (hmm...what was the key and what was the value in registry...). DOORS install does not create these registry values.
An alternative method is to use the -addins switch for the DOORS icon properties, e.g. -addins "\\server\dxlshare".
Could you please tell me how to configure the custom DXL on several client installations. It shouldnt overwrite the default addins from administrator.
Any help is appreciated.
thanks,
Rani
|
|